Exported ability to set GRT seed in a flow variable#4372
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a new configuration variable, GRT_SEED, which allows users to specify a random seed for global routing. The changes include documenting the new variable in FlowVariables.md, defining its schema in variables.json and variables.yaml, and implementing the logic in global_route.tcl to apply the seed using set_global_routing_random during the global routing stage. There are no review comments, and I have no additional feedback to provide.
| - grt | ||
| GRT_SEED: | ||
| description: > | ||
| Global route seed |
There was a problem hiding this comment.
Updated to match GPL_RANDOM_SEED description. Note that https://openroad.readthedocs.io/en/latest/main/src/grt/README.html#set-global-routing-randomness doesn't say much either.
There was a problem hiding this comment.
I don't see a new commit - forgot to push or label?
There was a problem hiding this comment.
Forgot to resync to public. Will do so after latest change goes through private CI.
tclfmt fix Updated variables.json updated GRT_SEED desc minor tweak to trigger Jenkins Signed-off-by: Jeff Ng <jeffng@precisioninno.com>
c2cf816 to
85e4ee0
Compare
2 participants
Was interested in running a seed sweep using the AutoTuner, so enabling the ability to set the GRT seed through a flow variable.
@eder-matheus is this the proper way to do this in GRT?
@maliberty FYI. I ran idecode through a six seed sweep and am running is_int through the same.